home *** CD-ROM | disk | FTP | other *** search
- Path: news.cis.nctu.edu.tw!usenet
- From: terryt@mcs.com (Terry Trippany)
- Newsgroups: comp.lang.c++
- Subject: Re: Why are 32 bit better than 16 bit pgms?
- Date: 19 Jan 1996 19:21:49 GMT
- Organization: STR/Baxter Labs
- Message-ID: <4dor0d$fj3@news.cis.nctu.edu.tw>
- References: <4djtqn$j96@news1.usa.pipeline.com>
- NNTP-Posting-Host: @159.198.73.111
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=US-ASCII
- X-Newsreader: WinVN 0.99.7
-
- In article <4djtqn$j96@news1.usa.pipeline.com>,
- grantp@usa.pipeline.com says...
- >
- >On Jan 16, 1996 11:43:34 in article <Why are 32 bit better than
- 16 bit
- >pgms?>, '"Keith S." <vain@netcom.com>' wrote:
- >
- >
- >>I have a simple questions:
- >>
- >>What's are 32 bit pgms better than 16 bit programs?
- >>
- >Better programmers generally produce better programs --
- >bitness doesn't come into play :-)
- >
- >Now, if you mean why we should develop 32-bit programs
- >rather than 16, there's many reasons. Here's a couple:
- >
- >1. 32-bit programs run faster.
-
- >
- >2. 32-bit programs are easier to write -- thereby increasing
- >programmer productivity.
- >
-
- While this may true when considering that you don't need LPSTRS
- and all window handles are now 32 bit, there are many
- considerations here.
-
- For instance, Windows NT is a preemptive, thread based OS. These
- issues are much more complex. The tools and libraries we use to
- write applications are now better.
-
- In NT we can have many instances of the same program. Thus shared
- memory becomes an issue. Disk access and file mapping is also to
- be considered.
-
- While these features are an inherent advantage in the 32 bit
- world, this doesn't necessarily make it easier.
-
- Many of the advantages of 32 bit windows applications are as
- follows:
-
- 1. 32 bit memory management. This removes any dependence on the
- x86 cpu, no segment/offset addressing methods.
-
- 2. Structured exception handling.
-
- 3. You break the 64k barrier.
-
- 4. File mapping - you can allocate a block of memory and associate
- it with a disk file. Thus the OS takes care of all the buffering,
- file opening, etc.
-
- 5. 16 bit windows limited your networking to non-blocking calls
- which necessitates polling or some kind of messaging scheme. With
- blocking calls, the OS can inform the application when the request
- is completed.
-
- 6. Subclassing has changed in Win32 in a way that pushes the
- developer into using OLE because you can no longer subclass a
- window or class that belongs to another process. This is more
- complex yet safer.
-
-
- The list goes on and on. In any case it would be advantageous in
- most cases to start porting your 16 bit applications to 32 bit,
- get comfortable with the new 32 bit api's, and learn the new
- complexities of the Win32 OS's if windows is your target.
-
- Hope this helps,
- Later
-
- /----------------------------------------------------------------\
- | Terry Trippany |
- | terryt@mcs.com |
- | Strategic Technology Resources |
- | Chicago, IL |
- | |
- | "A question asked is often a lesson learned" |
- \----------------------------------------------------------------/
-
-
-